Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 49decc25b8dfe6fed14ef1405da88337ca1c79480d555bf3a04078658edf5a2b

Tx prefix hash: c16029d729474c70fc20dbb9601c9a52ffa6a25649b0e13b0984bb5c9094dc88
Tx public key: c4846de1da9c95a6d0c588ca03138f12e9bb609714669a91317f1c25ae8c3b54
Timestamp: 1727586071 Timestamp [UCT]: 2024-09-29 05:01:11 Age [y:d:h:m:s]: 00:241:01:03:11
Block: 1120451 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 172123 RingCT/type: yes/0
Extra: 01c4846de1da9c95a6d0c588ca03138f12e9bb609714669a91317f1c25ae8c3b54021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d12d3f6bb81a5eb58450cb5d03d5ac49a1a86e61c6da106b1b1fd65258277a91 0.600000000000 1602370 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": 1120461, "vin": [ { "gen": { "height": 1120451 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d12d3f6bb81a5eb58450cb5d03d5ac49a1a86e61c6da106b1b1fd65258277a91" } } ], "extra": [ 1, 196, 132, 109, 225, 218, 156, 149, 166, 208, 197, 136, 202, 3, 19, 143, 18, 233, 187, 96, 151, 20, 102, 154, 145, 49, 127, 28, 37, 174, 140, 59, 84, 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