Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd7b74caf80b7bdbff4814918608e2cc19a8041c1d4d47d9ddf76f9f541520e6

Tx prefix hash: 3199ad29de229417fe2c7452df9932f4e8a1e244906a118b86ce7a981f404555
Tx public key: 29ecdb7a6cc61f612c43b32517948421a33f6d0f1fd67317d71f13ab11187e5f
Timestamp: 1704395710 Timestamp [UCT]: 2024-01-04 19:15:10 Age [y:d:h:m:s]: 01:098:23:55:47
Block: 928171 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 331877 RingCT/type: yes/0
Extra: 0129ecdb7a6cc61f612c43b32517948421a33f6d0f1fd67317d71f13ab11187e5f02110000000c59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3e8a47e3df0ae43364778d7bab0f4bbbccc9158b480599080c05007e3c1eb544 0.600000000000 1386029 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": 928181, "vin": [ { "gen": { "height": 928171 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3e8a47e3df0ae43364778d7bab0f4bbbccc9158b480599080c05007e3c1eb544" } } ], "extra": [ 1, 41, 236, 219, 122, 108, 198, 31, 97, 44, 67, 179, 37, 23, 148, 132, 33, 163, 63, 109, 15, 31, 214, 115, 23, 215, 31, 19, 171, 17, 24, 126, 95, 2, 17, 0, 0, 0, 12, 89, 218, 211, 245, 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