Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4cd0924db4ea7bf87c8e901578073cd5951aed575b5150cd16ca9e72cddbf5f9

Tx prefix hash: 3116c249ca82d531a20c7af5ec3a0d32336f076e5e273fdfdf7c8924dc0a0d07
Tx public key: 9dc9de459e01e8ea3ef5c2d71a5cf3181f5e83b64e7fda86ab18c76007577c7b
Timestamp: 1737479881 Timestamp [UCT]: 2025-01-21 17:18:01 Age [y:d:h:m:s]: 00:329:22:44:54
Block: 1202268 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 233411 RingCT/type: yes/0
Extra: 019dc9de459e01e8ea3ef5c2d71a5cf3181f5e83b64e7fda86ab18c76007577c7b0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 867a867f9f64dbb0e95b2b01b38da702a54d6977df14ad1808fc8596a0d1191e 0.600000000000 1688931 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": 1202278, "vin": [ { "gen": { "height": 1202268 } } ], "vout": [ { "amount": 600000000, "target": { "key": "867a867f9f64dbb0e95b2b01b38da702a54d6977df14ad1808fc8596a0d1191e" } } ], "extra": [ 1, 157, 201, 222, 69, 158, 1, 232, 234, 62, 245, 194, 215, 26, 92, 243, 24, 31, 94, 131, 182, 78, 127, 218, 134, 171, 24, 199, 96, 7, 87, 124, 123, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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