Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9708ad7a04b73aad7480f7f3c2d59b8535665cb96e39cb37e28c76dd84ee5481

Tx prefix hash: bf0acf3e80da105d4831e79ab1d8634f68f85816ca9c07fc093a8cf76339bf8c
Tx public key: 684721e5136c85c5e97e4130ec57ebc7b3311e8136c25be1f66391c189d68c92
Timestamp: 1725848872 Timestamp [UCT]: 2024-09-09 02:27:52 Age [y:d:h:m:s]: 00:080:09:23:16
Block: 1106045 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 57489 RingCT/type: yes/0
Extra: 01684721e5136c85c5e97e4130ec57ebc7b3311e8136c25be1f66391c189d68c9202110000000591e13c04000000000000000000

1 output(s) for total of 0.608040000000 dcy

stealth address amount amount idx
00: 4a5fd04a83755e7b0a5db57d4bda465de7a264128e2a2a03961268bcfce0f91d 0.608040000000 1583596 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": 1106055, "vin": [ { "gen": { "height": 1106045 } } ], "vout": [ { "amount": 608040000, "target": { "key": "4a5fd04a83755e7b0a5db57d4bda465de7a264128e2a2a03961268bcfce0f91d" } } ], "extra": [ 1, 104, 71, 33, 229, 19, 108, 133, 197, 233, 126, 65, 48, 236, 87, 235, 199, 179, 49, 30, 129, 54, 194, 91, 225, 246, 99, 145, 193, 137, 214, 140, 146, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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