Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af54e33215b3b5af8fcf32ff87ac13deb1c40a18ac240904a8526c17eb4d02c6

Tx prefix hash: c7da8d6cc11fee7524f41637a0f5a8589e558fab8a641a5aa2f5b9b45fbc1ce8
Tx public key: e961ae20bc9dcb0806c21d230741bd5d97e64dad0150e65e32a9bf8785399896
Timestamp: 1735415402 Timestamp [UCT]: 2024-12-28 19:50:02 Age [y:d:h:m:s]: 00:104:06:24:54
Block: 1185221 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74327 RingCT/type: yes/0
Extra: 01e961ae20bc9dcb0806c21d230741bd5d97e64dad0150e65e32a9bf8785399896021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 71c0d5d80248b0053b4f6f4af9fa2e40ae865f62135e83c06e8414df8ba8fae4 0.600000000000 1671688 of 15

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": 1185231, "vin": [ { "gen": { "height": 1185221 } } ], "vout": [ { "amount": 600000000, "target": { "key": "71c0d5d80248b0053b4f6f4af9fa2e40ae865f62135e83c06e8414df8ba8fae4" } } ], "extra": [ 1, 233, 97, 174, 32, 188, 157, 203, 8, 6, 194, 29, 35, 7, 65, 189, 93, 151, 230, 77, 173, 1, 80, 230, 94, 50, 169, 191, 135, 133, 57, 152, 150, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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