Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 18163794097407479458b27920d431d97dc6f418ab35e419e85007d37381df0a

Tx prefix hash: 6b83b80e62b5529b06da7e2db180fc3301a071f880960e6e74dd0e7f9da9f138
Tx public key: 31997102ea2b632f8482ec3d8aba58daa0a3f1feaa051ece15730d8de3ea129c
Timestamp: 1694791935 Timestamp [UCT]: 2023-09-15 15:32:15 Age [y:d:h:m:s]: 02:057:07:05:08
Block: 848758 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 560625 RingCT/type: yes/0
Extra: 0131997102ea2b632f8482ec3d8aba58daa0a3f1feaa051ece15730d8de3ea129c0211000000054b8f5122000000000000000000

1 output(s) for total of 0.945610897000 dcy

stealth address amount amount idx
00: ab7109c432776a8ae291a6a58dc2d951b1afa8a5a3ac0708c67c02298d000271 0.945610897000 1302384 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": 848768, "vin": [ { "gen": { "height": 848758 } } ], "vout": [ { "amount": 945610897, "target": { "key": "ab7109c432776a8ae291a6a58dc2d951b1afa8a5a3ac0708c67c02298d000271" } } ], "extra": [ 1, 49, 153, 113, 2, 234, 43, 99, 47, 132, 130, 236, 61, 138, 186, 88, 218, 160, 163, 241, 254, 170, 5, 30, 206, 21, 115, 13, 141, 227, 234, 18, 156, 2, 17, 0, 0, 0, 5, 75, 143, 81, 34, 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