Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e43a361cf182930872d9e3843ecca55c53855c05e906d0649bc639a2d5be827e

Tx prefix hash: 5142da9da879ec6d919c7a8dbaeeb0633f4e07ce8414eb0e7c4400d6727f0d7c
Tx public key: 99d01f80dfe08179b08f38b883cd174f92ae437d2b9239e6e8a4a4def5fde862
Timestamp: 1629422901 Timestamp [UCT]: 2021-08-20 01:28:21 Age [y:d:h:m:s]: 03:127:15:31:11
Block: 317387 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 864908 RingCT/type: yes/0
Extra: 0199d01f80dfe08179b08f38b883cd174f92ae437d2b9239e6e8a4a4def5fde86202110000001601f1e57f000000000000000000

1 output(s) for total of 54.496119725000 dcy

stealth address amount amount idx
00: d2209553d857029e6f5aa6c26b32b9a03df28a336ba0cec736f0b6d97a22fdf5 54.496119725000 659986 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": 317397, "vin": [ { "gen": { "height": 317387 } } ], "vout": [ { "amount": 54496119725, "target": { "key": "d2209553d857029e6f5aa6c26b32b9a03df28a336ba0cec736f0b6d97a22fdf5" } } ], "extra": [ 1, 153, 208, 31, 128, 223, 224, 129, 121, 176, 143, 56, 184, 131, 205, 23, 79, 146, 174, 67, 125, 43, 146, 57, 230, 232, 164, 164, 222, 245, 253, 232, 98, 2, 17, 0, 0, 0, 22, 1, 241, 229, 127, 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