Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1b4b2d0f7b81b81978a250f901d33cb04405f2a2ae54e79e2b78fe5249be98b8

Tx prefix hash: c51656fff28ff22579daef9afc108f3c7441f31cc063db5c5ff1a6c8ec4bc635
Tx public key: 52f4268b68400d81420de849cf66a668d6081f926df6b15dc6a424ede75d79a8
Timestamp: 1734170818 Timestamp [UCT]: 2024-12-14 10:06:58 Age [y:d:h:m:s]: 00:096:06:53:12
Block: 1174948 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68603 RingCT/type: yes/0
Extra: 0152f4268b68400d81420de849cf66a668d6081f926df6b15dc6a424ede75d79a80211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3f39955446510ee2c0eb8eb95217f082b6b11da6c5835b3e33017fb967902b42 0.600000000000 1661165 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": 1174958, "vin": [ { "gen": { "height": 1174948 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3f39955446510ee2c0eb8eb95217f082b6b11da6c5835b3e33017fb967902b42" } } ], "extra": [ 1, 82, 244, 38, 139, 104, 64, 13, 129, 66, 13, 232, 73, 207, 102, 166, 104, 214, 8, 31, 146, 109, 246, 177, 93, 198, 164, 36, 237, 231, 93, 121, 168, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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