Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 497d7205c444b318aa5a233315319be9fa11c12f1d9e877a6f73b74efaea5ef6

Tx prefix hash: f6c864eb4687eccc486a6002bac191a80443a26e0c3412ea569920ad1b7219d8
Tx public key: 361c5ddadb0bcfadf62fdcac0592d0f2cd918bd3045ed4cc339d8f3800f7d97b
Timestamp: 1714868717 Timestamp [UCT]: 2024-05-05 00:25:17 Age [y:d:h:m:s]: 01:025:03:16:51
Block: 1015021 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 278907 RingCT/type: yes/0
Extra: 01361c5ddadb0bcfadf62fdcac0592d0f2cd918bd3045ed4cc339d8f3800f7d97b0211000000070011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 902d49ce84bdbd17997ed8335770c0c2dff2acef57f2f3a06e61d3eea2600b1b 0.600000000000 1478272 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": 1015031, "vin": [ { "gen": { "height": 1015021 } } ], "vout": [ { "amount": 600000000, "target": { "key": "902d49ce84bdbd17997ed8335770c0c2dff2acef57f2f3a06e61d3eea2600b1b" } } ], "extra": [ 1, 54, 28, 93, 218, 219, 11, 207, 173, 246, 47, 220, 172, 5, 146, 208, 242, 205, 145, 139, 211, 4, 94, 212, 204, 51, 157, 143, 56, 0, 247, 217, 123, 2, 17, 0, 0, 0, 7, 0, 17, 5, 91, 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