Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d164b3a5c91ba9af49e9ba3ae3d91aeccc6242a1b09544e6169ee6ce6759b2ec

Tx prefix hash: 7404260406b4d80cdb4538b0d3ac1167b0168892f90e7e2df815af6ad39590ab
Tx public key: 54d2ee4b75c20f6732b5c69ab9e751376ca74a506f09dc9674d03dfc44c6de41
Timestamp: 1696936281 Timestamp [UCT]: 2023-10-10 11:11:21 Age [y:d:h:m:s]: 01:177:02:40:29
Block: 866554 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 387611 RingCT/type: yes/0
Extra: 0154d2ee4b75c20f6732b5c69ab9e751376ca74a506f09dc9674d03dfc44c6de41021100000001e08532b6000000000000000000

1 output(s) for total of 0.825556701000 dcy

stealth address amount amount idx
00: 10ff132800f85370485d0e8c4177265ca311fcbc69ffd1bb1546d4735bd91658 0.825556701000 1321160 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": 866564, "vin": [ { "gen": { "height": 866554 } } ], "vout": [ { "amount": 825556701, "target": { "key": "10ff132800f85370485d0e8c4177265ca311fcbc69ffd1bb1546d4735bd91658" } } ], "extra": [ 1, 84, 210, 238, 75, 117, 194, 15, 103, 50, 181, 198, 154, 185, 231, 81, 55, 108, 167, 74, 80, 111, 9, 220, 150, 116, 208, 61, 252, 68, 198, 222, 65, 2, 17, 0, 0, 0, 1, 224, 133, 50, 182, 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