Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a39b36968269f4b03590aaee6ceb1ad547ace0fe28f684a60644ddfb5dd6e3d6

Tx prefix hash: 61ee01f65f4f4832c1d31837f2f8f32f222502cd0911e303ef61e3b54bedfba8
Tx public key: 3225c0f80895d1b694dc589c04c3d4a73da383e34e221625c6f3460b0df8358d
Timestamp: 1738057655 Timestamp [UCT]: 2025-01-28 09:47:35 Age [y:d:h:m:s]: 00:141:20:10:21
Block: 1206860 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101287 RingCT/type: yes/0
Extra: 013225c0f80895d1b694dc589c04c3d4a73da383e34e221625c6f3460b0df8358d021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1f331df45917ff79817bef74dbfb3c04338cb78c4b89c9436af1392391b41cc9 0.600000000000 1693573 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": 1206870, "vin": [ { "gen": { "height": 1206860 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1f331df45917ff79817bef74dbfb3c04338cb78c4b89c9436af1392391b41cc9" } } ], "extra": [ 1, 50, 37, 192, 248, 8, 149, 209, 182, 148, 220, 88, 156, 4, 195, 212, 167, 61, 163, 131, 227, 78, 34, 22, 37, 198, 243, 70, 11, 13, 248, 53, 141, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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