Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8e7f060962397f9b4b5488c5423086e8795dbf1d07940d1745676e5e4cecc281

Tx prefix hash: 6485f069e62ec10bdb2b96ddb754968f8e7fdcf0c81ae7d32b39dbfb13a6a3d5
Tx public key: a3d8008193759af1389875d7a937591c58ab44b97ef36bd9100ac43ac0d6961b
Timestamp: 1617582648 Timestamp [UCT]: 2021-04-05 00:30:48 Age [y:d:h:m:s]: 03:310:18:19:35
Block: 233373 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 981604 RingCT/type: yes/0
Extra: 01a3d8008193759af1389875d7a937591c58ab44b97ef36bd9100ac43ac0d6961b02110000002c7071732b000000000000000000

1 output(s) for total of 103.452014001000 dcy

stealth address amount amount idx
00: bbaad71a56ef989167af98b9f221b04c4c0b8f12e4dc882d5bfd05786582148a 103.452014001000 484661 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": 233383, "vin": [ { "gen": { "height": 233373 } } ], "vout": [ { "amount": 103452014001, "target": { "key": "bbaad71a56ef989167af98b9f221b04c4c0b8f12e4dc882d5bfd05786582148a" } } ], "extra": [ 1, 163, 216, 0, 129, 147, 117, 154, 241, 56, 152, 117, 215, 169, 55, 89, 28, 88, 171, 68, 185, 126, 243, 107, 217, 16, 10, 196, 58, 192, 214, 150, 27, 2, 17, 0, 0, 0, 44, 112, 113, 115, 43, 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