Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 62fe2c02fa976e95b4ba66b4b417edff3c2282e2a8af098f451913cb60550700

Tx prefix hash: 0961575c5cb49634f5d7f4e0b81638d321731e2801dbf607cb6d8765731b62dc
Tx public key: 1eb5b05f828abe5cfd8db781f36afb343aa8ba995775f679ca5f07e87b15a993
Timestamp: 1726298881 Timestamp [UCT]: 2024-09-14 07:28:01 Age [y:d:h:m:s]: 00:162:03:47:22
Block: 1109771 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115687 RingCT/type: yes/0
Extra: 011eb5b05f828abe5cfd8db781f36afb343aa8ba995775f679ca5f07e87b15a99302110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eaa0ed266af7bc7f30869e59c5bfa9d36fc4d0f71de96c2aecfff1fdb68508b5 0.600000000000 1588146 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": 1109781, "vin": [ { "gen": { "height": 1109771 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eaa0ed266af7bc7f30869e59c5bfa9d36fc4d0f71de96c2aecfff1fdb68508b5" } } ], "extra": [ 1, 30, 181, 176, 95, 130, 138, 190, 92, 253, 141, 183, 129, 243, 106, 251, 52, 58, 168, 186, 153, 87, 117, 246, 121, 202, 95, 7, 232, 123, 21, 169, 147, 2, 17, 0, 0, 0, 1, 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