Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d8432390e82997e227e01f6a528cb03b091a3f548fecb4092b5a592691a92f63

Tx prefix hash: b44a2863cc673b029dd5a4b2a995b45581c11d1898dcf556601cddece4d9f56b
Tx public key: 1dae6dd4a773473bde82b804777cc5ae75d6e1d48165b7c90ad810bdcd633148
Timestamp: 1722387921 Timestamp [UCT]: 2024-07-31 01:05:21 Age [y:d:h:m:s]: 00:260:03:03:51
Block: 1077355 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185813 RingCT/type: yes/0
Extra: 011dae6dd4a773473bde82b804777cc5ae75d6e1d48165b7c90ad810bdcd63314802110000000a91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fa9dde569a1fa64cdec5d8a408b67b7c9c9fab18e2f912f224c6ba11af97ab51 0.600000000000 1549902 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": 1077365, "vin": [ { "gen": { "height": 1077355 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fa9dde569a1fa64cdec5d8a408b67b7c9c9fab18e2f912f224c6ba11af97ab51" } } ], "extra": [ 1, 29, 174, 109, 212, 167, 115, 71, 59, 222, 130, 184, 4, 119, 124, 197, 174, 117, 214, 225, 212, 129, 101, 183, 201, 10, 216, 16, 189, 205, 99, 49, 72, 2, 17, 0, 0, 0, 10, 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