Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b7f4e2cba86d07efeefa70fd13a9834be2ff14a492a9c8874e08390b9fe85a3

Tx prefix hash: e45d7e44f145f1f2628e5db311617a016dfe761a3139d1e2899d804308d91d51
Tx public key: 90452961a71325900ca43c101199009d098cb52f3c900c99b1c924f59ed25ea8
Timestamp: 1714529969 Timestamp [UCT]: 2024-05-01 02:19:29 Age [y:d:h:m:s]: 00:236:21:46:30
Block: 1012210 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 169582 RingCT/type: yes/0
Extra: 0190452961a71325900ca43c101199009d098cb52f3c900c99b1c924f59ed25ea80211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d4b39e7f601d3339408baed5059efc936e5e6801408e17af48b81d785e7bb65f 0.600000000000 1474664 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": 1012220, "vin": [ { "gen": { "height": 1012210 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d4b39e7f601d3339408baed5059efc936e5e6801408e17af48b81d785e7bb65f" } } ], "extra": [ 1, 144, 69, 41, 97, 167, 19, 37, 144, 12, 164, 60, 16, 17, 153, 0, 157, 9, 140, 181, 47, 60, 144, 12, 153, 177, 201, 36, 245, 158, 210, 94, 168, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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