Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5106fa0490722d082b2a841b2da5de7643af667a71a5bd6c045f3d95f9954d95

Tx prefix hash: f9698667caf3902fe8b81ad94563d42dbe2f4864ad8462e9491d6ed875e4678b
Tx public key: d49e2c9bbe9d63947a050a9969d15eb3fc4d4e8d87e32c8cb4b10acb358bda1f
Timestamp: 1740720119 Timestamp [UCT]: 2025-02-28 05:21:59 Age [y:d:h:m:s]: 00:265:21:47:54
Block: 1228867 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187795 RingCT/type: yes/0
Extra: 01d49e2c9bbe9d63947a050a9969d15eb3fc4d4e8d87e32c8cb4b10acb358bda1f0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 992b62152e48ec0bd03cfaa730e65db5c321d8b235fe527cf6b445612af133ae 0.600000000000 1715748 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": 1228877, "vin": [ { "gen": { "height": 1228867 } } ], "vout": [ { "amount": 600000000, "target": { "key": "992b62152e48ec0bd03cfaa730e65db5c321d8b235fe527cf6b445612af133ae" } } ], "extra": [ 1, 212, 158, 44, 155, 190, 157, 99, 148, 122, 5, 10, 153, 105, 209, 94, 179, 252, 77, 78, 141, 135, 227, 44, 140, 180, 177, 10, 203, 53, 139, 218, 31, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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