Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 78c40c80fa96dccac6b988567fa16e78a4c1331632db99ad76703c343acc331a

Tx prefix hash: 68cb293ee68e7470049d96ea417aa0389ba6a6422634e6634ea397716ad1f9b2
Tx public key: f84119a40602117d4054d829aaf1c3b409cb0ca26f06bc97489e5e3b2a1ab1fe
Timestamp: 1713035740 Timestamp [UCT]: 2024-04-13 19:15:40 Age [y:d:h:m:s]: 01:040:04:08:39
Block: 999792 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289713 RingCT/type: yes/0
Extra: 01f84119a40602117d4054d829aaf1c3b409cb0ca26f06bc97489e5e3b2a1ab1fe0211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bb44ab3b7d7d36caf9c1f803c4fa45b467141ed2a139918fe7de18f6f6e163ce 0.600000000000 1460276 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": 999802, "vin": [ { "gen": { "height": 999792 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb44ab3b7d7d36caf9c1f803c4fa45b467141ed2a139918fe7de18f6f6e163ce" } } ], "extra": [ 1, 248, 65, 25, 164, 6, 2, 17, 125, 64, 84, 216, 41, 170, 241, 195, 180, 9, 203, 12, 162, 111, 6, 188, 151, 72, 158, 94, 59, 42, 26, 177, 254, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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