Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e93936f73b6d9f5db48fa10d83bfd44668012ae1147704ae77f0d335cd7c92e0

Tx prefix hash: a364fda5b2a0af4d953a480778ab447ff9c35a34f60f97900a1ab9874ed7d1c8
Tx public key: 35ce58a7f26e521fc272cce3d96f5ca60936be481ee8fbdeabcdbec32dce9abc
Timestamp: 1676205764 Timestamp [UCT]: 2023-02-12 12:42:44 Age [y:d:h:m:s]: 02:057:14:51:50
Block: 695368 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 562784 RingCT/type: yes/0
Extra: 0135ce58a7f26e521fc272cce3d96f5ca60936be481ee8fbdeabcdbec32dce9abc021100000001faf35c9c000000000000000000

1 output(s) for total of 3.047593756000 dcy

stealth address amount amount idx
00: bbad07e5d45d10e20e2a378ac2f15adef4052a54012b4a9df41c2c3870347693 3.047593756000 1138323 of 0

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": 695378, "vin": [ { "gen": { "height": 695368 } } ], "vout": [ { "amount": 3047593756, "target": { "key": "bbad07e5d45d10e20e2a378ac2f15adef4052a54012b4a9df41c2c3870347693" } } ], "extra": [ 1, 53, 206, 88, 167, 242, 110, 82, 31, 194, 114, 204, 227, 217, 111, 92, 166, 9, 54, 190, 72, 30, 232, 251, 222, 171, 205, 190, 195, 45, 206, 154, 188, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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