Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 02f7455772c580efdc7ef4855af3e1ddaba5842fc09d35fde99c8421f95a839f

Tx prefix hash: 7348e3d8ccc9fd59a4e42ac188b9ace9452d19652a575e58befe312358c041b2
Tx public key: 78761cceb0b3c3b99a7bb20b98b2b8e0fa7567ba3d0cedc33b1f2ac3790fca57
Timestamp: 1727552470 Timestamp [UCT]: 2024-09-28 19:41:10 Age [y:d:h:m:s]: 00:228:16:31:48
Block: 1120171 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 163278 RingCT/type: yes/0
Extra: 0178761cceb0b3c3b99a7bb20b98b2b8e0fa7567ba3d0cedc33b1f2ac3790fca57021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 220161617fc571f2a1f9368f825594d820f10ff6035aade7c73c664caa0770ba 0.600000000000 1601992 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": 1120181, "vin": [ { "gen": { "height": 1120171 } } ], "vout": [ { "amount": 600000000, "target": { "key": "220161617fc571f2a1f9368f825594d820f10ff6035aade7c73c664caa0770ba" } } ], "extra": [ 1, 120, 118, 28, 206, 176, 179, 195, 185, 154, 123, 178, 11, 152, 178, 184, 224, 250, 117, 103, 186, 61, 12, 237, 195, 59, 31, 42, 195, 121, 15, 202, 87, 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