Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd6bbd8a957001ea9becd61ae731ec5cb5e55012901b6f4e2fb11f49220f6346

Tx prefix hash: 519c54c7f6cd2dcefbfe81466884ada336f9d0296891e2ceafc6e0b441dc7f11
Tx public key: 8475d857114d62a033246b17df8fb5ef71e535faa1b47c18dad967d64c98ea9f
Timestamp: 1695977513 Timestamp [UCT]: 2023-09-29 08:51:53 Age [y:d:h:m:s]: 01:106:14:45:43
Block: 858603 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 337465 RingCT/type: yes/0
Extra: 018475d857114d62a033246b17df8fb5ef71e535faa1b47c18dad967d64c98ea9f021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.877186384000 dcy

stealth address amount amount idx
00: adf2e1f56e66815357d16cc6a00f4c41f5ae15c995558514f738f5d17d48f8e9 0.877186384000 1312785 of 0

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": 858613, "vin": [ { "gen": { "height": 858603 } } ], "vout": [ { "amount": 877186384, "target": { "key": "adf2e1f56e66815357d16cc6a00f4c41f5ae15c995558514f738f5d17d48f8e9" } } ], "extra": [ 1, 132, 117, 216, 87, 17, 77, 98, 160, 51, 36, 107, 23, 223, 143, 181, 239, 113, 229, 53, 250, 161, 180, 124, 24, 218, 217, 103, 214, 76, 152, 234, 159, 2, 17, 0, 0, 0, 3, 230, 210, 127, 156, 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