Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a34bc009cd965644fb9d29b3d98543a75620dc5c55ef38c402928e3ef6b2d425

Tx prefix hash: 691f3d03b3690b91abd5c454901469c8098efaa36e5b69873283ac8e9f8339d7
Tx public key: e26558d19a2cb7b54e9790d68150697cc0c7270509cbcec5f9add695d53f323e
Timestamp: 1736416097 Timestamp [UCT]: 2025-01-09 09:48:17 Age [y:d:h:m:s]: 00:162:02:39:29
Block: 1193509 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115535 RingCT/type: yes/0
Extra: 01e26558d19a2cb7b54e9790d68150697cc0c7270509cbcec5f9add695d53f323e0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f0821c68e5e6f39b5b263ee37c9a9a069110bee718ff5c4c63d1333b99fd7907 0.600000000000 1680070 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": 1193519, "vin": [ { "gen": { "height": 1193509 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f0821c68e5e6f39b5b263ee37c9a9a069110bee718ff5c4c63d1333b99fd7907" } } ], "extra": [ 1, 226, 101, 88, 209, 154, 44, 183, 181, 78, 151, 144, 214, 129, 80, 105, 124, 192, 199, 39, 5, 9, 203, 206, 197, 249, 173, 214, 149, 213, 63, 50, 62, 2, 17, 0, 0, 0, 5, 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