Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 760b1f1225f9e3eebba5390d8b313857c2e65b3c656b3aea9b27a025d93f8c7a

Tx prefix hash: 5326240e5836c3e60596af929685a154efd63a18ca9b3fefb06eea20564e034e
Tx public key: 03680e16138bf1d134cc4ef4ce23e6f13475f853a34ac23f9ec9fb5ab1f473b3
Timestamp: 1736428771 Timestamp [UCT]: 2025-01-09 13:19:31 Age [y:d:h:m:s]: 00:162:00:38:50
Block: 1193625 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115471 RingCT/type: yes/0
Extra: 0103680e16138bf1d134cc4ef4ce23e6f13475f853a34ac23f9ec9fb5ab1f473b30211000000081f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 14a026a6a7618093b2d66c13de6ed3b42a7f3e278780d10d4cbb69cc61964231 0.600000000000 1680188 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": 1193635, "vin": [ { "gen": { "height": 1193625 } } ], "vout": [ { "amount": 600000000, "target": { "key": "14a026a6a7618093b2d66c13de6ed3b42a7f3e278780d10d4cbb69cc61964231" } } ], "extra": [ 1, 3, 104, 14, 22, 19, 139, 241, 209, 52, 204, 78, 244, 206, 35, 230, 241, 52, 117, 248, 83, 163, 74, 194, 63, 158, 201, 251, 90, 177, 244, 115, 179, 2, 17, 0, 0, 0, 8, 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