Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: da7423d6593903a14da7d49db6e7046effe31685c5bc0bb53669c1d9f0a9fcc2

Tx prefix hash: 040ef9b32838fbe15a8a996737e86b237c693f77636e28e90b7fd5b2e23c851a
Tx public key: 4a94e37eecd0495b5ea1ecc42b608266f39bbc81f0a3fdf0aa243106687bd89b
Timestamp: 1709104083 Timestamp [UCT]: 2024-02-28 07:08:03 Age [y:d:h:m:s]: 01:019:03:16:53
Block: 967233 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 274686 RingCT/type: yes/0
Extra: 014a94e37eecd0495b5ea1ecc42b608266f39bbc81f0a3fdf0aa243106687bd89b0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0eddf4e88a2feea5ed07d6aa8fca51b3dec2c9e2570576a4c6026608d05e06ae 0.600000000000 1427004 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": 967243, "vin": [ { "gen": { "height": 967233 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0eddf4e88a2feea5ed07d6aa8fca51b3dec2c9e2570576a4c6026608d05e06ae" } } ], "extra": [ 1, 74, 148, 227, 126, 236, 208, 73, 91, 94, 161, 236, 196, 43, 96, 130, 102, 243, 155, 188, 129, 240, 163, 253, 240, 170, 36, 49, 6, 104, 123, 216, 155, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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