Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a6f90ba3596de27865116bcf2cd11c85f33d485d1488347f3d8ddf2842c3b8be

Tx prefix hash: 0d0fcb27413f03dcc57a2e9820b9d3379f2d183ea32ed86f23b6a30eb59b0149
Tx public key: 43682dc07c7ce5e88757181bb7892eda3f8e1f04b868051c29b1aa37040af8ef
Timestamp: 1720170374 Timestamp [UCT]: 2024-07-05 09:06:14 Age [y:d:h:m:s]: 00:281:23:31:22
Block: 1058962 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201486 RingCT/type: yes/0
Extra: 0143682dc07c7ce5e88757181bb7892eda3f8e1f04b868051c29b1aa37040af8ef02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 51bed0c9d6a6d1fed344b2dfb7d0ffef71c186d3440f323f5e2073594d03aac4 0.600000000000 1529421 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": 1058972, "vin": [ { "gen": { "height": 1058962 } } ], "vout": [ { "amount": 600000000, "target": { "key": "51bed0c9d6a6d1fed344b2dfb7d0ffef71c186d3440f323f5e2073594d03aac4" } } ], "extra": [ 1, 67, 104, 45, 192, 124, 124, 229, 232, 135, 87, 24, 27, 183, 137, 46, 218, 63, 142, 31, 4, 184, 104, 5, 28, 41, 177, 170, 55, 4, 10, 248, 239, 2, 17, 0, 0, 0, 4, 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