Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a256464c91faa3ea428a8bad3304c6b24aaeb12f220b8fe80864966f04f9524

Tx prefix hash: 577ea50e5d85c9e6ba807f2212c01db6f2b6b0bb9a3d9b4d9332c86d5015f3b4
Tx public key: 7a908f561916342b8771d6897cb339a0e3129a0e5f6fa56f8951c9f87aa53d11
Timestamp: 1697963763 Timestamp [UCT]: 2023-10-22 08:36:03 Age [y:d:h:m:s]: 01:224:18:13:38
Block: 875070 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 421701 RingCT/type: yes/0
Extra: 017a908f561916342b8771d6897cb339a0e3129a0e5f6fa56f8951c9f87aa53d11021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.773623852000 dcy

stealth address amount amount idx
00: f815b32b3293ea64879ab14dad5e32fcd04a5e463d547a9fc113e0faef1865ff 0.773623852000 1330314 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": 875080, "vin": [ { "gen": { "height": 875070 } } ], "vout": [ { "amount": 773623852, "target": { "key": "f815b32b3293ea64879ab14dad5e32fcd04a5e463d547a9fc113e0faef1865ff" } } ], "extra": [ 1, 122, 144, 143, 86, 25, 22, 52, 43, 135, 113, 214, 137, 124, 179, 57, 160, 227, 18, 154, 14, 95, 111, 165, 111, 137, 81, 201, 248, 122, 165, 61, 17, 2, 17, 0, 0, 0, 4, 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