Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 08865040561e97cddea7ac2ed665818c52c443a47b8ca346e6cff7a1a0ebf3e8

Tx prefix hash: 9d45635d5ba7ca060cd594793e595b3fba595eba18c0f127c23609a242540e74
Tx public key: ec55a0f2f53a8bae61bb4d2454e3ebeeeafc33cc980dab53d76e3581ae05de3b
Timestamp: 1702623046 Timestamp [UCT]: 2023-12-15 06:50:46 Age [y:d:h:m:s]: 01:036:07:37:03
Block: 913484 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287281 RingCT/type: yes/0
Extra: 01ec55a0f2f53a8bae61bb4d2454e3ebeeeafc33cc980dab53d76e3581ae05de3b02110000000375e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8f41eb6c0dbdd37f067b7cb6abf63c179cf85fc4ece4cbb1a2edeb87cd323310 0.600000000000 1370752 of 15

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": 913494, "vin": [ { "gen": { "height": 913484 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8f41eb6c0dbdd37f067b7cb6abf63c179cf85fc4ece4cbb1a2edeb87cd323310" } } ], "extra": [ 1, 236, 85, 160, 242, 245, 58, 139, 174, 97, 187, 77, 36, 84, 227, 235, 238, 234, 252, 51, 204, 152, 13, 171, 83, 215, 110, 53, 129, 174, 5, 222, 59, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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