Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 351d295a8721745bae9b5c6531139b7e52a32abacc6f2312557c30c70e63aa41

Tx prefix hash: bb8c3e29df76736fe65f2b2a1102ed64e16a65577794f28efd36add5a34be043
Tx public key: 0d2dfe7e3c316657bfbcf8c80198efa80c503e22c530e0167b622312fe414d27
Timestamp: 1637570581 Timestamp [UCT]: 2021-11-22 08:43:01 Age [y:d:h:m:s]: 02:362:16:48:02
Block: 379556 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 777227 RingCT/type: yes/0
Extra: 010d2dfe7e3c316657bfbcf8c80198efa80c503e22c530e0167b622312fe414d27021100000002e9564d6f000000000000000000

1 output(s) for total of 33.913592089000 dcy

stealth address amount amount idx
00: cdd86a67b3bfe75e61ddb04e23fa0c8a8c351a28616ff7ec7a7c6e1ac5d087e0 33.913592089000 767204 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": 379566, "vin": [ { "gen": { "height": 379556 } } ], "vout": [ { "amount": 33913592089, "target": { "key": "cdd86a67b3bfe75e61ddb04e23fa0c8a8c351a28616ff7ec7a7c6e1ac5d087e0" } } ], "extra": [ 1, 13, 45, 254, 126, 60, 49, 102, 87, 191, 188, 248, 200, 1, 152, 239, 168, 12, 80, 62, 34, 197, 48, 224, 22, 123, 98, 35, 18, 254, 65, 77, 39, 2, 17, 0, 0, 0, 2, 233, 86, 77, 111, 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