Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f314b71272da9b97101f5b563837502fad0dfa92a0aff7085d18b2c2f00491b3

Tx prefix hash: faf6be38eaeee5c360afea2dc2cde5cbf51313388c307af44179580b392b705d
Tx public key: 8c75f3e447f6031c5fbe7754038943dff1a7bdf0fcd6fd248a3f1d0ffba7efe2
Timestamp: 1756765171 Timestamp [UCT]: 2025-09-01 22:19:31 Age [y:d:h:m:s]: 00:151:06:51:10
Block: 1359355 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108035 RingCT/type: yes/0
Extra: 018c75f3e447f6031c5fbe7754038943dff1a7bdf0fcd6fd248a3f1d0ffba7efe2021100000001ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d9b37395db8b1f18d956f5ceb5cdfd6c2a0912932ccf2c3f1a72931f1a8aa6e3 0.600000000000 1847368 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": 1359365, "vin": [ { "gen": { "height": 1359355 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d9b37395db8b1f18d956f5ceb5cdfd6c2a0912932ccf2c3f1a72931f1a8aa6e3" } } ], "extra": [ 1, 140, 117, 243, 228, 71, 246, 3, 28, 95, 190, 119, 84, 3, 137, 67, 223, 241, 167, 189, 240, 252, 214, 253, 36, 138, 63, 29, 15, 251, 167, 239, 226, 2, 17, 0, 0, 0, 1, 173, 121, 72, 208, 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