Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc01ad33f72727a00d063c268b0d312609d14dc9686cb15a0be7c479ff660c7c

Tx prefix hash: 35be526f3f4b72001d19baa8e0f8c921c66cd5ffdbea1bcd721b9465e2afe9dd
Tx public key: b48c20fb5fecf82153409b311c1a2e4201b1d1c744444723e545cfd0216af0a3
Timestamp: 1746335910 Timestamp [UCT]: 2025-05-04 05:18:30 Age [y:d:h:m:s]: 00:273:04:41:16
Block: 1275359 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 192893 RingCT/type: yes/0
Extra: 01b48c20fb5fecf82153409b311c1a2e4201b1d1c744444723e545cfd0216af0a302110000000d1f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d05b89911aa45ec58d0bb9c495cef07dc5b5fbf10d93cbfa866fa34e002d2487 0.600000000000 1762666 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": 1275369, "vin": [ { "gen": { "height": 1275359 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d05b89911aa45ec58d0bb9c495cef07dc5b5fbf10d93cbfa866fa34e002d2487" } } ], "extra": [ 1, 180, 140, 32, 251, 95, 236, 248, 33, 83, 64, 155, 49, 28, 26, 46, 66, 1, 177, 209, 199, 68, 68, 71, 35, 229, 69, 207, 208, 33, 106, 240, 163, 2, 17, 0, 0, 0, 13, 31, 144, 81, 122, 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