Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 926b290b31eac718dc79825ecfceb6c1a30732ee103f243a883c5081bcf728db

Tx prefix hash: 1dec47df016fbc347489ec7fee8d7df8001ec22bbd99710287a120b182c7bf41
Tx public key: 630c25b839317de4e035d6e76aa93527b136d4b78aa27236c2110680dfe720b1
Timestamp: 1723071267 Timestamp [UCT]: 2024-08-07 22:54:27 Age [y:d:h:m:s]: 00:246:00:02:40
Block: 1083016 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175706 RingCT/type: yes/0
Extra: 01630c25b839317de4e035d6e76aa93527b136d4b78aa27236c2110680dfe720b102110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7cfe0c8217e9fc41278e679d42ac6f3e87a8a8420f67dbb7ba8d01fba3f84a50 0.600000000000 1556851 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": 1083026, "vin": [ { "gen": { "height": 1083016 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7cfe0c8217e9fc41278e679d42ac6f3e87a8a8420f67dbb7ba8d01fba3f84a50" } } ], "extra": [ 1, 99, 12, 37, 184, 57, 49, 125, 228, 224, 53, 214, 231, 106, 169, 53, 39, 177, 54, 212, 183, 138, 162, 114, 54, 194, 17, 6, 128, 223, 231, 32, 177, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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