Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a32da416ee31ce227b818ba1f0501f2354d554d0522fc48e758860c0bfb22809

Tx prefix hash: a2ffe41b79592496f270291943b9b6931128b4f36a308e87d2ed511644d88830
Tx public key: 72bf8f1fa4c018bbe88f1daaf8e025dac6132a1187a8a42fe2e812340f9dc0d5
Timestamp: 1716191700 Timestamp [UCT]: 2024-05-20 07:55:00 Age [y:d:h:m:s]: 00:332:23:02:31
Block: 1025980 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237995 RingCT/type: yes/0
Extra: 0172bf8f1fa4c018bbe88f1daaf8e025dac6132a1187a8a42fe2e812340f9dc0d50211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8adb1f081332380956ae302b213c55d78754f731fbc2a9f084177458c28b091a 0.600000000000 1492813 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": 1025990, "vin": [ { "gen": { "height": 1025980 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8adb1f081332380956ae302b213c55d78754f731fbc2a9f084177458c28b091a" } } ], "extra": [ 1, 114, 191, 143, 31, 164, 192, 24, 187, 232, 143, 29, 170, 248, 224, 37, 218, 198, 19, 42, 17, 135, 168, 164, 47, 226, 232, 18, 52, 15, 157, 192, 213, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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