Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae411a02da9a1e2041afa282626139e656b776834efce45c63ff9600c9efe27d

Tx prefix hash: 246dc4a168d7eb0a8d36427aa4155689ecf68983fb7b077df39aa744c1a87ed0
Tx public key: 3e5a3a904ae420b14c11a791b42f2cdb9bf62a27f61142a09cfe0e21a96138fc
Timestamp: 1718801120 Timestamp [UCT]: 2024-06-19 12:45:20 Age [y:d:h:m:s]: 01:141:07:33:35
Block: 1047619 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 359546 RingCT/type: yes/0
Extra: 013e5a3a904ae420b14c11a791b42f2cdb9bf62a27f61142a09cfe0e21a96138fc0211000000020bba16d7000000000000000000

1 output(s) for total of 0.613580000000 dcy

stealth address amount amount idx
00: de41e8724217fa6c7737664e8b8ff5fcdbfe2657926d2551549005bcb424181e 0.613580000000 1517486 of 0

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": 1047629, "vin": [ { "gen": { "height": 1047619 } } ], "vout": [ { "amount": 613580000, "target": { "key": "de41e8724217fa6c7737664e8b8ff5fcdbfe2657926d2551549005bcb424181e" } } ], "extra": [ 1, 62, 90, 58, 144, 74, 228, 32, 177, 76, 17, 167, 145, 180, 47, 44, 219, 155, 246, 42, 39, 246, 17, 66, 160, 156, 254, 14, 33, 169, 97, 56, 252, 2, 17, 0, 0, 0, 2, 11, 186, 22, 215, 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