Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c684467665404a0439031470065bf479d3b392bad37a8d55bd59fd767b7c3df5

Tx prefix hash: 1a785437bfc82ed64143de23f9765ed3c80f009eb67c3099a818f5f98a42576d
Tx public key: 1bdeeb3473a8377974a1b2d1f4f7c48665b473fd6b3620c3e68544b23d590083
Timestamp: 1727704188 Timestamp [UCT]: 2024-09-30 13:49:48 Age [y:d:h:m:s]: 00:054:18:11:22
Block: 1121435 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 39117 RingCT/type: yes/0
Extra: 011bdeeb3473a8377974a1b2d1f4f7c48665b473fd6b3620c3e68544b23d59008302110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b5f5546cbb572c768998040cb2986ae3b6c423d4c167e7aa0a77d19fdb14463e 0.600000000000 1603698 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": 1121445, "vin": [ { "gen": { "height": 1121435 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b5f5546cbb572c768998040cb2986ae3b6c423d4c167e7aa0a77d19fdb14463e" } } ], "extra": [ 1, 27, 222, 235, 52, 115, 168, 55, 121, 116, 161, 178, 209, 244, 247, 196, 134, 101, 180, 115, 253, 107, 54, 32, 195, 230, 133, 68, 178, 61, 89, 0, 131, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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