Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bfcfcdc08199a31a3e32f57fbfa0a7d837b8de81866c973619a22c3010df85dc

Tx prefix hash: bf16c393bbd92176b51e551e62ef0f38318d9e0bfbea95f979529f5b153355d9
Tx public key: 34a83653a21060e031a580f23b26c975916287eeb41dcb3269776e4807961ac1
Timestamp: 1745636196 Timestamp [UCT]: 2025-04-26 02:56:36 Age [y:d:h:m:s]: 00:204:16:31:47
Block: 1269573 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 144010 RingCT/type: yes/0
Extra: 0134a83653a21060e031a580f23b26c975916287eeb41dcb3269776e4807961ac1021100000003dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0a8c3f0b740670f3fe9a670e627de98c0a9a6e0fb3868cd44c234f46b1a3caa3 0.600000000000 1756812 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": 1269583, "vin": [ { "gen": { "height": 1269573 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a8c3f0b740670f3fe9a670e627de98c0a9a6e0fb3868cd44c234f46b1a3caa3" } } ], "extra": [ 1, 52, 168, 54, 83, 162, 16, 96, 224, 49, 165, 128, 242, 59, 38, 201, 117, 145, 98, 135, 238, 180, 29, 203, 50, 105, 119, 110, 72, 7, 150, 26, 193, 2, 17, 0, 0, 0, 3, 219, 181, 113, 193, 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