Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 20597cb12517756e1b1a321bdd1d622310aedc90b3c03c267fec57e5a944c4ae

Tx prefix hash: e20eb5fb5847c166a5e11bd86d41b136c1a93a44a1e4f5c1f33247154ec3d9ec
Tx public key: 2c3fe0e0f58d5c8c46541d530d8ae79ea0c04cad7444b24d2b497fb29f30c92e
Timestamp: 1705045730 Timestamp [UCT]: 2024-01-12 07:48:50 Age [y:d:h:m:s]: 01:097:10:17:27
Block: 933554 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 330755 RingCT/type: yes/0
Extra: 012c3fe0e0f58d5c8c46541d530d8ae79ea0c04cad7444b24d2b497fb29f30c92e02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 45cd5c18777ef04e7cdde9c7d510a64fcfc30dc9841f78abed352e0584e9ae1b 0.600000000000 1391518 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": 933564, "vin": [ { "gen": { "height": 933554 } } ], "vout": [ { "amount": 600000000, "target": { "key": "45cd5c18777ef04e7cdde9c7d510a64fcfc30dc9841f78abed352e0584e9ae1b" } } ], "extra": [ 1, 44, 63, 224, 224, 245, 141, 92, 140, 70, 84, 29, 83, 13, 138, 231, 158, 160, 192, 76, 173, 116, 68, 178, 77, 43, 73, 127, 178, 159, 48, 201, 46, 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