Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1c244924bb432a2574d49690b47641f34118c25a85df47290aa4adac738c23b

Tx prefix hash: 4db72f67c8a8536b512943ac90cf374cdcc3178d34f6e818deacb236bdb0f655
Tx public key: 84e5b166e94870271db22e6a8fa0996ff0e37952e6e5bf25f118f6974a0bcb8a
Timestamp: 1674970151 Timestamp [UCT]: 2023-01-29 05:29:11 Age [y:d:h:m:s]: 01:295:06:56:55
Block: 685100 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 472010 RingCT/type: yes/0
Extra: 0184e5b166e94870271db22e6a8fa0996ff0e37952e6e5bf25f118f6974a0bcb8a02110000000175e3f0e9000000000000000000

1 output(s) for total of 3.295939541000 dcy

stealth address amount amount idx
00: ab44fe649c1abcd64447eae59ac25573b03632a2feb020903df8e2352ea1cb7d 3.295939541000 1127389 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": 685110, "vin": [ { "gen": { "height": 685100 } } ], "vout": [ { "amount": 3295939541, "target": { "key": "ab44fe649c1abcd64447eae59ac25573b03632a2feb020903df8e2352ea1cb7d" } } ], "extra": [ 1, 132, 229, 177, 102, 233, 72, 112, 39, 29, 178, 46, 106, 143, 160, 153, 111, 240, 227, 121, 82, 230, 229, 191, 37, 241, 24, 246, 151, 74, 11, 203, 138, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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