Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b7f463974228f6fc28287c6f1888128906504101070636e8c4a12384410bc283

Tx prefix hash: 6e2aa456202d4f456f7ac4e35f30b0d2d00737ab2749e792a686fa4690293b12
Tx public key: ab4a780b518715ab93872f7a6a88b27ac7a7f7c2eb04293168ec517faeb8d0eb
Timestamp: 1673142149 Timestamp [UCT]: 2023-01-08 01:42:29 Age [y:d:h:m:s]: 02:098:17:26:00
Block: 669944 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 592244 RingCT/type: yes/0
Extra: 01ab4a780b518715ab93872f7a6a88b27ac7a7f7c2eb04293168ec517faeb8d0eb021100000001faf35c9c000000000000000000

1 output(s) for total of 3.699962976000 dcy

stealth address amount amount idx
00: c01fc5ed4d09e93a3fc44ee6c85dea1e4b56e21dc17691e888caedfbe96aac0b 3.699962976000 1111311 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": 669954, "vin": [ { "gen": { "height": 669944 } } ], "vout": [ { "amount": 3699962976, "target": { "key": "c01fc5ed4d09e93a3fc44ee6c85dea1e4b56e21dc17691e888caedfbe96aac0b" } } ], "extra": [ 1, 171, 74, 120, 11, 81, 135, 21, 171, 147, 135, 47, 122, 106, 136, 178, 122, 199, 167, 247, 194, 235, 4, 41, 49, 104, 236, 81, 127, 174, 184, 208, 235, 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