Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 367db8b01a22665258e3cad122bcce5388c94e14e613dc46f8966476e5b1d0c7

Tx prefix hash: c6a200e0344e2ac2715f9bed965c710bcc68947d4358a91cd6f6a49cb8d789f6
Tx public key: c8443f01dd25b99c952cada0c90a4036e5ad307198ea04e4f9e10343c515f2eb
Timestamp: 1703533423 Timestamp [UCT]: 2023-12-25 19:43:43 Age [y:d:h:m:s]: 01:062:03:48:51
Block: 921046 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 305499 RingCT/type: yes/0
Extra: 01c8443f01dd25b99c952cada0c90a4036e5ad307198ea04e4f9e10343c515f2eb02110000001859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c9cac214a6a487aba2bbbef728db6299b2e1574b98cc6aa8a1ad3326949b2757 0.600000000000 1378730 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": 921056, "vin": [ { "gen": { "height": 921046 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c9cac214a6a487aba2bbbef728db6299b2e1574b98cc6aa8a1ad3326949b2757" } } ], "extra": [ 1, 200, 68, 63, 1, 221, 37, 185, 156, 149, 44, 173, 160, 201, 10, 64, 54, 229, 173, 48, 113, 152, 234, 4, 228, 249, 225, 3, 67, 197, 21, 242, 235, 2, 17, 0, 0, 0, 24, 89, 218, 211, 245, 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