Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 81715d6d7988bf4babeac89c904e49d85857f211ecdd242901460149f6b4f5ba

Tx prefix hash: dd942c9ecfa11a9b70316011cf70e1431a62caf5677d716d91bc0f08128eecac
Tx public key: d21a83740fc8f18c77494c3e825ce3fd2c79996f55886e9c25a7fb1fe3f0bb5f
Timestamp: 1698254098 Timestamp [UCT]: 2023-10-25 17:14:58 Age [y:d:h:m:s]: 01:148:10:32:50
Block: 877488 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 367078 RingCT/type: yes/0
Extra: 01d21a83740fc8f18c77494c3e825ce3fd2c79996f55886e9c25a7fb1fe3f0bb5f021100000005e6d27f9c000000000000000000

1 output(s) for total of 0.759482917000 dcy

stealth address amount amount idx
00: 28bb27ee9fb19e2a9ab9d7ca1ef4b0b7430fddb5849a26042d2014cd59125d0c 0.759482917000 1332864 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": 877498, "vin": [ { "gen": { "height": 877488 } } ], "vout": [ { "amount": 759482917, "target": { "key": "28bb27ee9fb19e2a9ab9d7ca1ef4b0b7430fddb5849a26042d2014cd59125d0c" } } ], "extra": [ 1, 210, 26, 131, 116, 15, 200, 241, 140, 119, 73, 76, 62, 130, 92, 227, 253, 44, 121, 153, 111, 85, 136, 110, 156, 37, 167, 251, 31, 227, 240, 187, 95, 2, 17, 0, 0, 0, 5, 230, 210, 127, 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