Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f8e4099e8d0166e16fc986bba12d1ddda24451509efbf24d5d8323ac4ef5cc8f

Tx prefix hash: 76c2566fa5537f4e2676f7edffc37041888643b6537db35b71a5c66529e6c28a
Tx public key: 245e909429d1c7d1c20a7e965dccb9943de154ab7b02d5adb65a1feadc6529a9
Timestamp: 1717396231 Timestamp [UCT]: 2024-06-03 06:30:31 Age [y:d:h:m:s]: 00:177:23:19:23
Block: 1035984 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 127364 RingCT/type: yes/0
Extra: 01245e909429d1c7d1c20a7e965dccb9943de154ab7b02d5adb65a1feadc6529a902110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 40005bbc38fb68263034e4c46e5b68c341b46e45077e7edf89062a8282982be4 0.600000000000 1504509 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": 1035994, "vin": [ { "gen": { "height": 1035984 } } ], "vout": [ { "amount": 600000000, "target": { "key": "40005bbc38fb68263034e4c46e5b68c341b46e45077e7edf89062a8282982be4" } } ], "extra": [ 1, 36, 94, 144, 148, 41, 209, 199, 209, 194, 10, 126, 150, 93, 204, 185, 148, 61, 225, 84, 171, 123, 2, 213, 173, 182, 90, 31, 234, 220, 101, 41, 169, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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