Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 005c78c032f5f7c71e429aea25a9f7d9f7a587fadb485af5079b9f979efc5988

Tx prefix hash: 4205097e2cf5e02fe13ea3d1ce8752bbb360497f9caec2b36c18ad2f3842fcea
Tx public key: dd0a4367d513b6fd161b4dced3402c25e9fc28b8e8001e5976dde218fde57923
Timestamp: 1699807419 Timestamp [UCT]: 2023-11-12 16:43:39 Age [y:d:h:m:s]: 01:192:22:45:47
Block: 890154 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 399118 RingCT/type: yes/0
Extra: 01dd0a4367d513b6fd161b4dced3402c25e9fc28b8e8001e5976dde218fde57923021100000007faf35c9c000000000000000000

1 output(s) for total of 0.689525410000 dcy

stealth address amount amount idx
00: 3f7dff685966ac6ff929819ed2ba7142dbbb89a1ab9eb92442ef8689964ef50d 0.689525410000 1346175 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": 890164, "vin": [ { "gen": { "height": 890154 } } ], "vout": [ { "amount": 689525410, "target": { "key": "3f7dff685966ac6ff929819ed2ba7142dbbb89a1ab9eb92442ef8689964ef50d" } } ], "extra": [ 1, 221, 10, 67, 103, 213, 19, 182, 253, 22, 27, 77, 206, 211, 64, 44, 37, 233, 252, 40, 184, 232, 0, 30, 89, 118, 221, 226, 24, 253, 229, 121, 35, 2, 17, 0, 0, 0, 7, 250, 243, 92, 156, 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