Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bef0925bff74ab80603b67ce1e3efa33dc8ae2ff43a8fb26e49d1dad2231a075

Tx prefix hash: 8f1e9b9cf53f785feb06a5c0066367db3aeb2136a90e351bf01672edaab411c8
Tx public key: 0a270aa847597e442c14fcae79ab0388c969f645fc8caf6defa5fec39b633e5f
Timestamp: 1694319757 Timestamp [UCT]: 2023-09-10 04:22:37 Age [y:d:h:m:s]: 02:057:21:28:16
Block: 844834 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 561047 RingCT/type: yes/0
Extra: 010a270aa847597e442c14fcae79ab0388c969f645fc8caf6defa5fec39b633e5f021100000007e6d27f9c000000000000000000

1 output(s) for total of 0.974348487000 dcy

stealth address amount amount idx
00: 7446c743db984fcaa0f24d851d6921ec6cfad3b3ee5632ed5b97d55e2b477317 0.974348487000 1298168 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": 844844, "vin": [ { "gen": { "height": 844834 } } ], "vout": [ { "amount": 974348487, "target": { "key": "7446c743db984fcaa0f24d851d6921ec6cfad3b3ee5632ed5b97d55e2b477317" } } ], "extra": [ 1, 10, 39, 10, 168, 71, 89, 126, 68, 44, 20, 252, 174, 121, 171, 3, 136, 201, 105, 246, 69, 252, 140, 175, 109, 239, 165, 254, 195, 155, 99, 62, 95, 2, 17, 0, 0, 0, 7, 230, 210, 127, 156, 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