Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: afd0a334e0558eb3cdfc49822828d9572199d926f976d887afff30e61ad62337

Tx prefix hash: a40d0e3578e5dca5719ebfe7180c056344f1f6fa575fa38f9dbfdaa4c6654afc
Tx public key: 027bba86ae3865d4e3e9fa6c4defb69297e2d4b2ada5a5e222cc0a7f046e9410
Timestamp: 1695824093 Timestamp [UCT]: 2023-09-27 14:14:53 Age [y:d:h:m:s]: 01:126:04:17:42
Block: 857321 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 351214 RingCT/type: yes/0
Extra: 01027bba86ae3865d4e3e9fa6c4defb69297e2d4b2ada5a5e222cc0a7f046e9410021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.885808171000 dcy

stealth address amount amount idx
00: 96006ae04dc4839f473b16b5ba2f8f114091ae3316c1e215fc7d28553b04f946 0.885808171000 1311437 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": 857331, "vin": [ { "gen": { "height": 857321 } } ], "vout": [ { "amount": 885808171, "target": { "key": "96006ae04dc4839f473b16b5ba2f8f114091ae3316c1e215fc7d28553b04f946" } } ], "extra": [ 1, 2, 123, 186, 134, 174, 56, 101, 212, 227, 233, 250, 108, 77, 239, 182, 146, 151, 226, 212, 178, 173, 165, 165, 226, 34, 204, 10, 127, 4, 110, 148, 16, 2, 17, 0, 0, 0, 1, 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