Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4bea8f1dc67eda4b1eafbcdeb2ffd3909383667fc4aa6074196fdd415a45b8bb

Tx prefix hash: f63076a321cf624944a81dbfb63a53cc5881f8a3eb3bb37b39fc5081e8811d67
Tx public key: 604703114fbec33178643aa498d0fb32f6afc89e791a3e9aaa20163d9acbe1a2
Timestamp: 1679495932 Timestamp [UCT]: 2023-03-22 14:38:52 Age [y:d:h:m:s]: 02:042:19:39:42
Block: 722658 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 552146 RingCT/type: yes/0
Extra: 01604703114fbec33178643aa498d0fb32f6afc89e791a3e9aaa20163d9acbe1a2021100000001faf35c9c000000000000000000

1 output(s) for total of 2.474764836000 dcy

stealth address amount amount idx
00: a9dbd7b9e5ca5e71cac2d93a1b38d2fabb482092faffd6f59a8200d5e526a110 2.474764836000 1167601 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": 722668, "vin": [ { "gen": { "height": 722658 } } ], "vout": [ { "amount": 2474764836, "target": { "key": "a9dbd7b9e5ca5e71cac2d93a1b38d2fabb482092faffd6f59a8200d5e526a110" } } ], "extra": [ 1, 96, 71, 3, 17, 79, 190, 195, 49, 120, 100, 58, 164, 152, 208, 251, 50, 246, 175, 200, 158, 121, 26, 62, 154, 170, 32, 22, 61, 154, 203, 225, 162, 2, 17, 0, 0, 0, 1, 250, 243, 92, 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