Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cfa1c03834d81ed87f9710d29086270885bfebd1731c9518f2ff05fc20adfb1c

Tx prefix hash: c1ff9eb14a6ec52d76566cd11f1c3c696f714d4b384516fb8b9a36aacc93067f
Tx public key: 0bbeae3d27b15d02f2c8e4b211ab1444a404b34dc466a421b5dc3ed1ebd020c2
Timestamp: 1737753342 Timestamp [UCT]: 2025-01-24 21:15:42 Age [y:d:h:m:s]: 00:048:20:02:48
Block: 1204534 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 34731 RingCT/type: yes/0
Extra: 010bbeae3d27b15d02f2c8e4b211ab1444a404b34dc466a421b5dc3ed1ebd020c20211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 268147ddc69ceaf2a9e7b9780f02e6cef20f7c9075d27f3cb592a5cd381df99a 0.600000000000 1691221 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": 1204544, "vin": [ { "gen": { "height": 1204534 } } ], "vout": [ { "amount": 600000000, "target": { "key": "268147ddc69ceaf2a9e7b9780f02e6cef20f7c9075d27f3cb592a5cd381df99a" } } ], "extra": [ 1, 11, 190, 174, 61, 39, 177, 93, 2, 242, 200, 228, 178, 17, 171, 20, 68, 164, 4, 179, 77, 196, 102, 164, 33, 181, 220, 62, 209, 235, 208, 32, 194, 2, 17, 0, 0, 0, 4, 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