Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b478dde54b5b5d71c2b13871f77afca17b5fff2b10d9c1df89ad6462d8b6051f

Tx prefix hash: a57e4d5583a36c649bcf06e9f92d938f8543e3ec8101828d1ca3b2626665b697
Tx public key: 64d6cfddec7beaf2c29df3bfa656369dbeb3c7f2f4931db315af10f86db192f2
Timestamp: 1705378897 Timestamp [UCT]: 2024-01-16 04:21:37 Age [y:d:h:m:s]: 01:300:08:44:43
Block: 936317 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 473496 RingCT/type: yes/0
Extra: 0164d6cfddec7beaf2c29df3bfa656369dbeb3c7f2f4931db315af10f86db192f20211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 323049d6b94390a77be54c241e60f985f7dcfeccda41b4cc60038c9eeda01e7a 0.600000000000 1394341 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": 936327, "vin": [ { "gen": { "height": 936317 } } ], "vout": [ { "amount": 600000000, "target": { "key": "323049d6b94390a77be54c241e60f985f7dcfeccda41b4cc60038c9eeda01e7a" } } ], "extra": [ 1, 100, 214, 207, 221, 236, 123, 234, 242, 194, 157, 243, 191, 166, 86, 54, 157, 190, 179, 199, 242, 244, 147, 29, 179, 21, 175, 16, 248, 109, 177, 146, 242, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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