Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 65bfec22289814a71fb3cb23a2830c22db813163a9cc299a0642569cdf108e18

Tx prefix hash: 3774663599a8bc830eb9fae198b3e7894c8da5da6c8ffff7366d02c9a787ee1d
Tx public key: c4c5fb4eb013d84b0e7441d073431c5567494bc5cb56c934f862f9fa801e60ea
Timestamp: 1701655291 Timestamp [UCT]: 2023-12-04 02:01:31 Age [y:d:h:m:s]: 01:102:21:22:16
Block: 905463 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 334712 RingCT/type: yes/0
Extra: 01c4c5fb4eb013d84b0e7441d073431c5567494bc5cb56c934f862f9fa801e60ea021100000005e6d27f9c000000000000000000

1 output(s) for total of 0.613514994000 dcy

stealth address amount amount idx
00: 2a3fee07e1e32a560df7110ae040e69aa43aee9e11f7317550ce80ffabec27ef 0.613514994000 1362350 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": 905473, "vin": [ { "gen": { "height": 905463 } } ], "vout": [ { "amount": 613514994, "target": { "key": "2a3fee07e1e32a560df7110ae040e69aa43aee9e11f7317550ce80ffabec27ef" } } ], "extra": [ 1, 196, 197, 251, 78, 176, 19, 216, 75, 14, 116, 65, 208, 115, 67, 28, 85, 103, 73, 75, 197, 203, 86, 201, 52, 248, 98, 249, 250, 128, 30, 96, 234, 2, 17, 0, 0, 0, 5, 230, 210, 127, 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