Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e42dab3c498c77971164763e458588affed7ae7ea3aafe4a2259c9b727ec1d7

Tx prefix hash: 867d6ad2d088a86055abe2a86727d06e4a74803d2aa0d3d78da41720a08d74c5
Tx public key: 057f0d303767f27d1003016a986647e27fc9882ecab721e9cbf3f164f3c004b0
Timestamp: 1695831229 Timestamp [UCT]: 2023-09-27 16:13:49 Age [y:d:h:m:s]: 02:037:20:03:02
Block: 857388 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 546663 RingCT/type: yes/0
Extra: 01057f0d303767f27d1003016a986647e27fc9882ecab721e9cbf3f164f3c004b0021100000003faf35c9c000000000000000000

1 output(s) for total of 0.885355487000 dcy

stealth address amount amount idx
00: ddde4e99146e67ad6dc659849f21364fdc328f0155cd9babbe72db9cfedb34ce 0.885355487000 1311506 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": 857398, "vin": [ { "gen": { "height": 857388 } } ], "vout": [ { "amount": 885355487, "target": { "key": "ddde4e99146e67ad6dc659849f21364fdc328f0155cd9babbe72db9cfedb34ce" } } ], "extra": [ 1, 5, 127, 13, 48, 55, 103, 242, 125, 16, 3, 1, 106, 152, 102, 71, 226, 127, 201, 136, 46, 202, 183, 33, 233, 203, 243, 241, 100, 243, 192, 4, 176, 2, 17, 0, 0, 0, 3, 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