Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4aa176bef2fbb8e4f34043d67c32368c55cafae6713ffd2984393d364086447e

Tx prefix hash: 0951758e266fa5e2429ad3ffbce021a766c1da419eb13a6fa51c6d2d8c0f7168
Tx public key: 73056410b5f3b84afa5b88ebb2ae59f153911a90f5da0aaed1c8bbab9f4fe8e7
Timestamp: 1721726307 Timestamp [UCT]: 2024-07-23 09:18:27 Age [y:d:h:m:s]: 00:279:10:45:53
Block: 1071858 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 199670 RingCT/type: yes/0
Extra: 0173056410b5f3b84afa5b88ebb2ae59f153911a90f5da0aaed1c8bbab9f4fe8e70211000000018f454fe7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e40e972fecfa691cccaa7c173bb354d567c0492e96e5974999427b2f7bfd84be 0.600000000000 1544243 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": 1071868, "vin": [ { "gen": { "height": 1071858 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e40e972fecfa691cccaa7c173bb354d567c0492e96e5974999427b2f7bfd84be" } } ], "extra": [ 1, 115, 5, 100, 16, 181, 243, 184, 74, 250, 91, 136, 235, 178, 174, 89, 241, 83, 145, 26, 144, 245, 218, 10, 174, 209, 200, 187, 171, 159, 79, 232, 231, 2, 17, 0, 0, 0, 1, 143, 69, 79, 231, 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