Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 77c5fbc5139cf64447eb962d50f24741721a207d67a1c4793aafbf5f514ece06

Tx prefix hash: d4df60429937bff3c35c9ad78925f1f1b529c349c36a8c5dd81c276d4518195c
Tx public key: 17212622a04c6b03b9e333c9f5d562704dc854b5b4ab3187d4c6766314ec7f44
Timestamp: 1731393568 Timestamp [UCT]: 2024-11-12 06:39:28 Age [y:d:h:m:s]: 00:143:09:40:40
Block: 1151914 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102325 RingCT/type: yes/0
Extra: 0117212622a04c6b03b9e333c9f5d562704dc854b5b4ab3187d4c6766314ec7f44021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dd397bdc41d0e83e8cf4e0f639854912b715b8756e63a2bcc03ad8ba49246681 0.600000000000 1637497 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": 1151924, "vin": [ { "gen": { "height": 1151914 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd397bdc41d0e83e8cf4e0f639854912b715b8756e63a2bcc03ad8ba49246681" } } ], "extra": [ 1, 23, 33, 38, 34, 160, 76, 107, 3, 185, 227, 51, 201, 245, 213, 98, 112, 77, 200, 84, 181, 180, 171, 49, 135, 212, 198, 118, 99, 20, 236, 127, 68, 2, 17, 0, 0, 0, 3, 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