Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fbc8ef39b4df0f543f357b7978480aa4cbd46653dbeaf5181e9944426a23de9c

Tx prefix hash: b228ad9fb5e4f50416b8cebadd2f9e599febb52609e9d98c6a7079cdd98aa3cc
Tx public key: cb61e5853f948cc009d21e0a0f71c00509eb3751941c700069bb0fc8f99ef3a8
Timestamp: 1736550452 Timestamp [UCT]: 2025-01-10 23:07:32 Age [y:d:h:m:s]: 00:345:14:31:45
Block: 1194619 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 244563 RingCT/type: yes/0
Extra: 01cb61e5853f948cc009d21e0a0f71c00509eb3751941c700069bb0fc8f99ef3a8021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 151e20ff423a561e425199e77ed0f3df5a64c8c5eb1b6b1e36cf9baa5634a851 0.600000000000 1681196 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": 1194629, "vin": [ { "gen": { "height": 1194619 } } ], "vout": [ { "amount": 600000000, "target": { "key": "151e20ff423a561e425199e77ed0f3df5a64c8c5eb1b6b1e36cf9baa5634a851" } } ], "extra": [ 1, 203, 97, 229, 133, 63, 148, 140, 192, 9, 210, 30, 10, 15, 113, 192, 5, 9, 235, 55, 81, 148, 28, 112, 0, 105, 187, 15, 200, 249, 158, 243, 168, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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