Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5bc22ee6c8c04d7b9408ffb6d03fb05e33c01cbeeba734d6d25a0c75f22642fd

Tx prefix hash: 103b6f3ce4eeb852e98b1325e31d98b67ce3834d15645e22a6c01e0d2cfbeed5
Tx public key: 0183da9ae051742fdff46452566ac0c67c3bc45b6e3deea8d30860f767a61fa5
Timestamp: 1578184950 Timestamp [UCT]: 2020-01-05 00:42:30 Age [y:d:h:m:s]: 04:329:13:39:33
Block: 38879 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1124733 RingCT/type: yes/0
Extra: 010183da9ae051742fdff46452566ac0c67c3bc45b6e3deea8d30860f767a61fa502110000001317786bcf000000000000000000

1 output(s) for total of 456.297487883000 dcy

stealth address amount amount idx
00: 3b729fbed9c6a3500d4d7f2ff908d2617b08ec0d9b1679804928adf70f56b8de 456.297487883000 66616 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": 38889, "vin": [ { "gen": { "height": 38879 } } ], "vout": [ { "amount": 456297487883, "target": { "key": "3b729fbed9c6a3500d4d7f2ff908d2617b08ec0d9b1679804928adf70f56b8de" } } ], "extra": [ 1, 1, 131, 218, 154, 224, 81, 116, 47, 223, 244, 100, 82, 86, 106, 192, 198, 124, 59, 196, 91, 110, 61, 238, 168, 211, 8, 96, 247, 103, 166, 31, 165, 2, 17, 0, 0, 0, 19, 23, 120, 107, 207, 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