Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ffe0245ddece13f38c07c2adaabef7fd8e6f840fca609351816b8c779d62868b

Tx prefix hash: b849d5610b5ada3dbf61beae7dcbbf34d7c5bc80338dd13353cd4291bfe77b6f
Tx public key: aebcfa23f004f0f2f1ae0a1c6d889475e55716f3a703505a589b81ab33cb7648
Timestamp: 1673255721 Timestamp [UCT]: 2023-01-09 09:15:21 Age [y:d:h:m:s]: 02:092:06:23:03
Block: 670877 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 587631 RingCT/type: yes/0
Extra: 01aebcfa23f004f0f2f1ae0a1c6d889475e55716f3a703505a589b81ab33cb7648021100000001faf35c9c000000000000000000

1 output(s) for total of 3.673759222000 dcy

stealth address amount amount idx
00: d6e1003d4bde17ccddf147c7841a09e119c690a45305320ba229704d38adf097 3.673759222000 1112298 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": 670887, "vin": [ { "gen": { "height": 670877 } } ], "vout": [ { "amount": 3673759222, "target": { "key": "d6e1003d4bde17ccddf147c7841a09e119c690a45305320ba229704d38adf097" } } ], "extra": [ 1, 174, 188, 250, 35, 240, 4, 240, 242, 241, 174, 10, 28, 109, 136, 148, 117, 229, 87, 22, 243, 167, 3, 80, 90, 88, 155, 129, 171, 51, 203, 118, 72, 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