Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 240def905a3e90a2e606c6cec0b6be190436896acecee2676832b3cd9825d1a2

Tx prefix hash: cc502588f6ea40a729a8a0421a611aef99ebebe50c8a695bd9d5c8e76bf9fe46
Tx public key: 2ef26414c2d53f3ad68c2507a16eb2efa6feb483cee565ad7819c0c3b9669c1b
Timestamp: 1673210064 Timestamp [UCT]: 2023-01-08 20:34:24 Age [y:d:h:m:s]: 02:303:01:13:08
Block: 670495 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 735994 RingCT/type: yes/0
Extra: 012ef26414c2d53f3ad68c2507a16eb2efa6feb483cee565ad7819c0c3b9669c1b02110000000252542ceb000000000000000000

1 output(s) for total of 3.684441673000 dcy

stealth address amount amount idx
00: e592ac8d3ef6dab1784615738b2a6ad2a20299e633e22fc8fdd17899260ceae7 3.684441673000 1111904 of 0

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": 670505, "vin": [ { "gen": { "height": 670495 } } ], "vout": [ { "amount": 3684441673, "target": { "key": "e592ac8d3ef6dab1784615738b2a6ad2a20299e633e22fc8fdd17899260ceae7" } } ], "extra": [ 1, 46, 242, 100, 20, 194, 213, 63, 58, 214, 140, 37, 7, 161, 110, 178, 239, 166, 254, 180, 131, 206, 229, 101, 173, 120, 25, 192, 195, 185, 102, 156, 27, 2, 17, 0, 0, 0, 2, 82, 84, 44, 235, 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