Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 62e0fa3b5de52d9bb6026dadf9275730cc89796b952a0a3ec219f9b0b3384332

Tx prefix hash: 33419e8c84cf2b57d93e12c11ec94bc24bdf8a86face8cda7a807b0ef4f1132e
Tx public key: 169f685fceca1c0724525d6ad0f1ac54ed477b86bb5d0beac7238d3a221f8097
Timestamp: 1702392834 Timestamp [UCT]: 2023-12-12 14:53:54 Age [y:d:h:m:s]: 01:144:13:44:51
Block: 911601 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 364455 RingCT/type: yes/0
Extra: 01169f685fceca1c0724525d6ad0f1ac54ed477b86bb5d0beac7238d3a221f8097021100000002faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d06084e6b35f4ad4ae2d2dfc4d632f6e6468ae85abb886655d70177676f5d96b 0.600000000000 1368815 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": 911611, "vin": [ { "gen": { "height": 911601 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d06084e6b35f4ad4ae2d2dfc4d632f6e6468ae85abb886655d70177676f5d96b" } } ], "extra": [ 1, 22, 159, 104, 95, 206, 202, 28, 7, 36, 82, 93, 106, 208, 241, 172, 84, 237, 71, 123, 134, 187, 93, 11, 234, 199, 35, 141, 58, 34, 31, 128, 151, 2, 17, 0, 0, 0, 2, 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