Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a409447182293d0841bdd25e12ca1b5044fc39878a13bc3af5ead08de71a25f5

Tx prefix hash: aee0485b3bec783c0b5faf13b152ff6cb0a706eab6f370b5397a56365e73c588
Tx public key: 0a76568adb0bc30d88f6b4cc72ea845f3e13c336ff15ef659e7bbbe748d5ab51
Timestamp: 1729112840 Timestamp [UCT]: 2024-10-16 21:07:20 Age [y:d:h:m:s]: 00:038:06:22:50
Block: 1133107 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 27311 RingCT/type: yes/0
Extra: 010a76568adb0bc30d88f6b4cc72ea845f3e13c336ff15ef659e7bbbe748d5ab5102110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3d50f29cf4e3ca21fd713535b06117b7985bea25fe8984f819d61d2276aa920b 0.600000000000 1616176 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": 1133117, "vin": [ { "gen": { "height": 1133107 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3d50f29cf4e3ca21fd713535b06117b7985bea25fe8984f819d61d2276aa920b" } } ], "extra": [ 1, 10, 118, 86, 138, 219, 11, 195, 13, 136, 246, 180, 204, 114, 234, 132, 95, 62, 19, 195, 54, 255, 21, 239, 101, 158, 123, 187, 231, 72, 213, 171, 81, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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