Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9730a9418b1ca11fc71e7b9b12de53aff5d865ea0d78e2890944d8b98b8d99a2

Tx prefix hash: b8c4f783d58172f37f6ceff6aa7effc4c09b283e785253d100b2010e92acbddb
Tx public key: 4643cc4827fc316533c612f09b3a0fe87c2436c4e23fd7a267a5cd00b67a259b
Timestamp: 1718554679 Timestamp [UCT]: 2024-06-16 16:17:59 Age [y:d:h:m:s]: 00:222:07:24:40
Block: 1045592 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 159018 RingCT/type: yes/0
Extra: 014643cc4827fc316533c612f09b3a0fe87c2436c4e23fd7a267a5cd00b67a259b02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e3f96861acae010a06df880eab82981e39626e2a5908c516b48891be4affded6 0.600000000000 1515203 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": 1045602, "vin": [ { "gen": { "height": 1045592 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e3f96861acae010a06df880eab82981e39626e2a5908c516b48891be4affded6" } } ], "extra": [ 1, 70, 67, 204, 72, 39, 252, 49, 101, 51, 198, 18, 240, 155, 58, 15, 232, 124, 36, 54, 196, 226, 63, 215, 162, 103, 165, 205, 0, 182, 122, 37, 155, 2, 17, 0, 0, 0, 1, 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