Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a606ade3801dcbbaf315744eefa97b8de50bb4903bdb80d798f0164977af2a40

Tx prefix hash: 50be6e9f2df005502f6a630c0ca07919bdbfd82c5349096663bcc54aecfc2a91
Tx public key: aa9b5b5127150815e8c46ef0f3ac85db68e59d6104568227985c3ea40a6a0531
Timestamp: 1705093463 Timestamp [UCT]: 2024-01-12 21:04:23 Age [y:d:h:m:s]: 01:044:10:36:19
Block: 933953 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 292828 RingCT/type: yes/0
Extra: 01aa9b5b5127150815e8c46ef0f3ac85db68e59d6104568227985c3ea40a6a05310211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 42df76fd41fef54b1d4d262f5d8d6f41dfc5f4d903323250f3325c7c52ee0f79 0.600000000000 1391937 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": 933963, "vin": [ { "gen": { "height": 933953 } } ], "vout": [ { "amount": 600000000, "target": { "key": "42df76fd41fef54b1d4d262f5d8d6f41dfc5f4d903323250f3325c7c52ee0f79" } } ], "extra": [ 1, 170, 155, 91, 81, 39, 21, 8, 21, 232, 196, 110, 240, 243, 172, 133, 219, 104, 229, 157, 97, 4, 86, 130, 39, 152, 92, 62, 164, 10, 106, 5, 49, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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