Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7858c017adc51241d9d3c43fdd3d3853f4ac68a9d54a74eab24713e1b90b6360

Tx prefix hash: 1eefa31f919b2073bc430ccb043e29454c75e321bcd627b8ad25b6479789f1c1
Tx public key: b41e08368a17d8384524e972ea44ba74d0d0599ce5b323865ff4fb9aceecb161
Timestamp: 1720061094 Timestamp [UCT]: 2024-07-04 02:44:54 Age [y:d:h:m:s]: 00:294:03:47:56
Block: 1058058 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210198 RingCT/type: yes/0
Extra: 01b41e08368a17d8384524e972ea44ba74d0d0599ce5b323865ff4fb9aceecb1610211000000030cce0636000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1df6570a5e7984cf0452ea4f057bc276a9e32f7f5db41b69ddcc92fc9db393e3 0.600000000000 1528507 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": 1058068, "vin": [ { "gen": { "height": 1058058 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1df6570a5e7984cf0452ea4f057bc276a9e32f7f5db41b69ddcc92fc9db393e3" } } ], "extra": [ 1, 180, 30, 8, 54, 138, 23, 216, 56, 69, 36, 233, 114, 234, 68, 186, 116, 208, 208, 89, 156, 229, 179, 35, 134, 95, 244, 251, 154, 206, 236, 177, 97, 2, 17, 0, 0, 0, 3, 12, 206, 6, 54, 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