Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7639d313d8c6b478141cbdd7421782d5f760a743a049a17d78d964473b078593

Tx prefix hash: d955ed8376d7a02c1192a66343d1a38d21b7875912c46e05888cf98f391fcd68
Tx public key: b64d8db0e149f095c1f93e2be84ac80f58276a1bb984c01b3cad243f1782d55d
Timestamp: 1712702937 Timestamp [UCT]: 2024-04-09 22:48:57 Age [y:d:h:m:s]: 00:347:08:33:03
Block: 997038 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 248349 RingCT/type: yes/0
Extra: 01b64d8db0e149f095c1f93e2be84ac80f58276a1bb984c01b3cad243f1782d55d02110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 41cc26f403ae49b47d727a9bc4ad49a1fcd988dca0ef9fe206ce7305286c49ea 0.600000000000 1457466 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": 997048, "vin": [ { "gen": { "height": 997038 } } ], "vout": [ { "amount": 600000000, "target": { "key": "41cc26f403ae49b47d727a9bc4ad49a1fcd988dca0ef9fe206ce7305286c49ea" } } ], "extra": [ 1, 182, 77, 141, 176, 225, 73, 240, 149, 193, 249, 62, 43, 232, 74, 200, 15, 88, 39, 106, 27, 185, 132, 192, 27, 60, 173, 36, 63, 23, 130, 213, 93, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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