Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 987feeef5cb1619e466fd04a7f5633b0c2c54d264a1d93b7666cb4c1eb5952b6

Tx prefix hash: 32586c8be972b96cb6f9e436c76df3f46b215a9adb4fe88df4816d946d8b9dce
Tx public key: 7c377cade237724fdcb9b5a442bb80a2a573d5d1af68e5f2f8bf27e29adc7aa1
Timestamp: 1716734910 Timestamp [UCT]: 2024-05-26 14:48:30 Age [y:d:h:m:s]: 00:303:03:44:04
Block: 1030503 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 216648 RingCT/type: yes/0
Extra: 017c377cade237724fdcb9b5a442bb80a2a573d5d1af68e5f2f8bf27e29adc7aa10211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2e38663f7186df6bb7698a86259f4f844caeab4359074ef854a746afb6cf7319 0.600000000000 1498758 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": 1030513, "vin": [ { "gen": { "height": 1030503 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2e38663f7186df6bb7698a86259f4f844caeab4359074ef854a746afb6cf7319" } } ], "extra": [ 1, 124, 55, 124, 173, 226, 55, 114, 79, 220, 185, 181, 164, 66, 187, 128, 162, 165, 115, 213, 209, 175, 104, 229, 242, 248, 191, 39, 226, 154, 220, 122, 161, 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