Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 84a856f131515be6cff112c648feb348eb0a7669e343de875cc570679c7d009e

Tx prefix hash: 525f9554e10f8004a8dc567996d7a620a1b8e4e8932628f17fdb07ae4f5fabd1
Tx public key: fafb0aa4886c537f65a5aaaa61a80f2a4fe0feaeb66fdf052899c9a7433ae052
Timestamp: 1713063627 Timestamp [UCT]: 2024-04-14 03:00:27 Age [y:d:h:m:s]: 01:205:08:44:50
Block: 1000028 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 405442 RingCT/type: yes/0
Extra: 01fafb0aa4886c537f65a5aaaa61a80f2a4fe0feaeb66fdf052899c9a7433ae05202110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 39278a0415c9cc6b996593cfff5b24779a034a526d5e515dba489af1b714f7ee 0.600000000000 1460518 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": 1000038, "vin": [ { "gen": { "height": 1000028 } } ], "vout": [ { "amount": 600000000, "target": { "key": "39278a0415c9cc6b996593cfff5b24779a034a526d5e515dba489af1b714f7ee" } } ], "extra": [ 1, 250, 251, 10, 164, 136, 108, 83, 127, 101, 165, 170, 170, 97, 168, 15, 42, 79, 224, 254, 174, 182, 111, 223, 5, 40, 153, 201, 167, 67, 58, 224, 82, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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