Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0bc41eff25e794e9e659a017dd8a1bb626e28aa41327be260511ca9a034fefc4

Tx prefix hash: 9f14523bb9c5404065ecabf38003d12ce235d718d1c55d3cbe62142e0e57fde2
Tx public key: e583fedb519b4228cdd26a3033ff1a26dcbd136f15e1eae0c1b06c139fe56fe0
Timestamp: 1737399403 Timestamp [UCT]: 2025-01-20 18:56:43 Age [y:d:h:m:s]: 00:148:17:35:11
Block: 1201614 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106043 RingCT/type: yes/0
Extra: 01e583fedb519b4228cdd26a3033ff1a26dcbd136f15e1eae0c1b06c139fe56fe0021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3f0792f0959367b30b3b8d08107b2575f7277ed234f25a28f3d314f22122bb1b 0.600000000000 1688269 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": 1201624, "vin": [ { "gen": { "height": 1201614 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3f0792f0959367b30b3b8d08107b2575f7277ed234f25a28f3d314f22122bb1b" } } ], "extra": [ 1, 229, 131, 254, 219, 81, 155, 66, 40, 205, 210, 106, 48, 51, 255, 26, 38, 220, 189, 19, 111, 21, 225, 234, 224, 193, 176, 108, 19, 159, 229, 111, 224, 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