Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 42a61174f2edb75ab2a5649482df9b7084c91c8b6b13368869516e2b49eace8d

Tx prefix hash: bb03c209f697440094cdc026d372c5c678469d5e972a89bef12d84a5d9f2efc6
Tx public key: 7e2cfdc983fcd26607fa646f008f207f049d31b9e96d5bbb870dcd4ee488a687
Timestamp: 1715915627 Timestamp [UCT]: 2024-05-17 03:13:47 Age [y:d:h:m:s]: 00:326:06:34:42
Block: 1023701 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 233194 RingCT/type: yes/0
Extra: 017e2cfdc983fcd26607fa646f008f207f049d31b9e96d5bbb870dcd4ee488a68702110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b727c727d8ca59648934f9bb65ebeb0db9af3beebe0f88bb04a0e093b910512e 0.600000000000 1488872 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1023711, "vin": [ { "gen": { "height": 1023701 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b727c727d8ca59648934f9bb65ebeb0db9af3beebe0f88bb04a0e093b910512e" } } ], "extra": [ 1, 126, 44, 253, 201, 131, 252, 210, 102, 7, 250, 100, 111, 0, 143, 32, 127, 4, 157, 49, 185, 233, 109, 91, 187, 135, 13, 205, 78, 228, 136, 166, 135, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8