Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b1fc261a02f2323dc7c41385148dfc501e19b5bab132bc0d2e46f383cda2975f

Tx prefix hash: 77de4d2605558849d02d3f9da924ebb4362a2dd732029e7a8dd10d90c52a8079
Tx public key: 384bc334056e486f168243472c8193ea18b4b525c9eddb0c2a259a9db712f07b
Timestamp: 1735883292 Timestamp [UCT]: 2025-01-03 05:48:12 Age [y:d:h:m:s]: 00:351:20:47:36
Block: 1189115 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 249028 RingCT/type: yes/0
Extra: 01384bc334056e486f168243472c8193ea18b4b525c9eddb0c2a259a9db712f07b021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 97e97ad4e3cd3b273ba45e2c5235881defd1f8d80b7201f082525e37ad250cdd 0.600000000000 1675620 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": 1189125, "vin": [ { "gen": { "height": 1189115 } } ], "vout": [ { "amount": 600000000, "target": { "key": "97e97ad4e3cd3b273ba45e2c5235881defd1f8d80b7201f082525e37ad250cdd" } } ], "extra": [ 1, 56, 75, 195, 52, 5, 110, 72, 111, 22, 130, 67, 71, 44, 129, 147, 234, 24, 180, 181, 37, 201, 237, 219, 12, 42, 37, 154, 157, 183, 18, 240, 123, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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