Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d7b63220c635d4bb2b7a33195afeb43ef50281db59cd7e258c2b6b31d73ee9e6

Tx prefix hash: 8723f70eec6b2020746c7e14e761d0eaaa8d99342c9eae7a032a73008a42d12d
Tx public key: 6bfe593a0f0afe463a699fc9a1e1e3f8e7f9db049cd710546b8b38c420254bc1
Timestamp: 1724042531 Timestamp [UCT]: 2024-08-19 04:42:11 Age [y:d:h:m:s]: 00:207:18:46:06
Block: 1091081 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 148366 RingCT/type: yes/0
Extra: 016bfe593a0f0afe463a699fc9a1e1e3f8e7f9db049cd710546b8b38c420254bc1021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1da061255ecd65aaf129a731431f01a5e4759b20de4d45b5dd26a1c9dcf80c38 0.600000000000 1565706 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": 1091091, "vin": [ { "gen": { "height": 1091081 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1da061255ecd65aaf129a731431f01a5e4759b20de4d45b5dd26a1c9dcf80c38" } } ], "extra": [ 1, 107, 254, 89, 58, 15, 10, 254, 70, 58, 105, 159, 201, 161, 225, 227, 248, 231, 249, 219, 4, 156, 215, 16, 84, 107, 139, 56, 196, 32, 37, 75, 193, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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