Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aaeca871b1630d64275eb7a50309c4d10e6ee570944f6185b6c7c0c92cb69f73

Tx prefix hash: 2f161d36a159e1ca35b19fb27055597a5b304d9511301569afccd7e4063ecb28
Tx public key: d56afabef5a475962b86577dca11a7daee8fbb095f4dcde85aa73b62a3411c7b
Timestamp: 1708939191 Timestamp [UCT]: 2024-02-26 09:19:51 Age [y:d:h:m:s]: 01:281:06:16:36
Block: 965866 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 459792 RingCT/type: yes/0
Extra: 01d56afabef5a475962b86577dca11a7daee8fbb095f4dcde85aa73b62a3411c7b02110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2493feac1f021dce4f50ba754136a2c61cd11cf90d6aa7cdad04c5cd80b9f255 0.600000000000 1425621 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": 965876, "vin": [ { "gen": { "height": 965866 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2493feac1f021dce4f50ba754136a2c61cd11cf90d6aa7cdad04c5cd80b9f255" } } ], "extra": [ 1, 213, 106, 250, 190, 245, 164, 117, 150, 43, 134, 87, 125, 202, 17, 167, 218, 238, 143, 187, 9, 95, 77, 205, 232, 90, 167, 59, 98, 163, 65, 28, 123, 2, 17, 0, 0, 0, 5, 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