Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 795aca17475832a37162c402dcbb19fa3bea5b381912f015f5162b8bbeb8a4dd

Tx prefix hash: 677b927b474bbfd75e23f4b539d23f57c3a53548a686bc98cc503a9630a91293
Tx public key: 8c1db581fab83deafc3af094b90d323c73460e82cc1841b993ca14f1d8405edc
Timestamp: 1723171085 Timestamp [UCT]: 2024-08-09 02:38:05 Age [y:d:h:m:s]: 00:252:16:32:07
Block: 1083835 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180506 RingCT/type: yes/0
Extra: 018c1db581fab83deafc3af094b90d323c73460e82cc1841b993ca14f1d8405edc02110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f541ba2e88c6ce81814b3932cb9849bb269523d9393f86f2e91384d5a6472034 0.600000000000 1557902 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": 1083845, "vin": [ { "gen": { "height": 1083835 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f541ba2e88c6ce81814b3932cb9849bb269523d9393f86f2e91384d5a6472034" } } ], "extra": [ 1, 140, 29, 181, 129, 250, 184, 61, 234, 252, 58, 240, 148, 185, 13, 50, 60, 115, 70, 14, 130, 204, 24, 65, 185, 147, 202, 20, 241, 216, 64, 94, 220, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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