Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ce171e5d8f263e93b53aa93f9b6b3ea692dc6516a02acea7852e6238ccb01d1a

Tx prefix hash: 0b1cd7dcb54dc92e8fe8c29461bdfcc83deb1d5f2deb8d11f4f55af74dd39cb1
Tx public key: 4de503a10d2c6ee1c1305dd4bb2293eeb836249219fa0e1c16bc854501bea1dd
Timestamp: 1744689413 Timestamp [UCT]: 2025-04-15 03:56:53 Age [y:d:h:m:s]: 00:264:09:30:10
Block: 1261739 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186767 RingCT/type: yes/0
Extra: 014de503a10d2c6ee1c1305dd4bb2293eeb836249219fa0e1c16bc854501bea1dd021100000001dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e1e704cead1e0aac6f184c77de3acba744872531fd2f4aee8d3b736ea2b60afc 0.600000000000 1748912 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": 1261749, "vin": [ { "gen": { "height": 1261739 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e1e704cead1e0aac6f184c77de3acba744872531fd2f4aee8d3b736ea2b60afc" } } ], "extra": [ 1, 77, 229, 3, 161, 13, 44, 110, 225, 193, 48, 93, 212, 187, 34, 147, 238, 184, 54, 36, 146, 25, 250, 14, 28, 22, 188, 133, 69, 1, 190, 161, 221, 2, 17, 0, 0, 0, 1, 219, 181, 113, 193, 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