Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa4b3f1d49b4eb82508ccdf5cf5c7eae77ffe57fd431b5830a3c8e95048c4051

Tx prefix hash: 1c85b8f0e0cbac980a431cb56b8daf55a611391ba0ba5839c37b67379b0e107a
Tx public key: 6acef9fa62ed25ecfca67e9786ff833bc80c57229e2114e27b1d2bb28fc551c3
Timestamp: 1733492500 Timestamp [UCT]: 2024-12-06 13:41:40 Age [y:d:h:m:s]: 00:340:12:19:48
Block: 1169314 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 240883 RingCT/type: yes/0
Extra: 016acef9fa62ed25ecfca67e9786ff833bc80c57229e2114e27b1d2bb28fc551c3021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cc8e00980aa80b6a9bd12a4aa58d67730f1cff05bf16ffdca0fe4c94d7f7ed6e 0.600000000000 1655029 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": 1169324, "vin": [ { "gen": { "height": 1169314 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cc8e00980aa80b6a9bd12a4aa58d67730f1cff05bf16ffdca0fe4c94d7f7ed6e" } } ], "extra": [ 1, 106, 206, 249, 250, 98, 237, 37, 236, 252, 166, 126, 151, 134, 255, 131, 59, 200, 12, 87, 34, 158, 33, 20, 226, 123, 29, 43, 178, 143, 197, 81, 195, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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