Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 966b5d559d723ee732b84b2ff1c36b311e08f63bdd9ce80d8ae68d910edd6647

Tx prefix hash: 3564496b883b47ad4c346a388e9b8e2ff895d5d860448b0fcc0d71aedda4eae5
Tx public key: 42dd4e4fa29fe3c986cc5b90703adc673648dd0f60735982db194797aa67a2d2
Timestamp: 1647812431 Timestamp [UCT]: 2022-03-20 21:40:31 Age [y:d:h:m:s]: 03:038:18:09:33
Block: 462790 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 807897 RingCT/type: yes/0
Extra: 0142dd4e4fa29fe3c986cc5b90703adc673648dd0f60735982db194797aa67a2d2021100000001bf7ee4e7000000000000000000

1 output(s) for total of 17.971522740000 dcy

stealth address amount amount idx
00: 491fcbc7b3fc1452c8be14a7b87bdc84e581081cc5d0314514eb7ec5a3f68b66 17.971522740000 880315 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": 462800, "vin": [ { "gen": { "height": 462790 } } ], "vout": [ { "amount": 17971522740, "target": { "key": "491fcbc7b3fc1452c8be14a7b87bdc84e581081cc5d0314514eb7ec5a3f68b66" } } ], "extra": [ 1, 66, 221, 78, 79, 162, 159, 227, 201, 134, 204, 91, 144, 112, 58, 220, 103, 54, 72, 221, 15, 96, 115, 89, 130, 219, 25, 71, 151, 170, 103, 162, 210, 2, 17, 0, 0, 0, 1, 191, 126, 228, 231, 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