Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed1cfc08b87804d99318189bf8f4ab75196fcfb6a1b8cf40f738ea4120cb6ee4

Tx prefix hash: 6e55cedfc2688d8b716fe0974a4f83f1c1cfa6f543a43dc1d241cdeca5b874b1
Tx public key: f41a4673fec400e43ca38a0bbc48579cf842b4696484c32b65c10f192b59863a
Timestamp: 1716992741 Timestamp [UCT]: 2024-05-29 14:25:41 Age [y:d:h:m:s]: 00:354:23:59:57
Block: 1032626 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 253752 RingCT/type: yes/0
Extra: 01f41a4673fec400e43ca38a0bbc48579cf842b4696484c32b65c10f192b59863a02110000000441ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f9301b97a0672baddf9bc0d9aa4fd79d33a1a514a173b03fd94acb78610a12f 0.600000000000 1501079 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": 1032636, "vin": [ { "gen": { "height": 1032626 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f9301b97a0672baddf9bc0d9aa4fd79d33a1a514a173b03fd94acb78610a12f" } } ], "extra": [ 1, 244, 26, 70, 115, 254, 196, 0, 228, 60, 163, 138, 11, 188, 72, 87, 156, 248, 66, 180, 105, 100, 132, 195, 43, 101, 193, 15, 25, 43, 89, 134, 58, 2, 17, 0, 0, 0, 4, 65, 238, 28, 155, 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