Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f3fc5cf0c09c8d0a976791ee042079e3c91d377d366060c99c0871c6590064cf

Tx prefix hash: 2b48553b7d304a4958a1f613718516af7568c28bc21eea44c9ca6b2e4f455549
Tx public key: 79f487cd8ba09619f382c1c55390a5a39babb0ae0d82e65c4fbc0fb642313aae
Timestamp: 1735202609 Timestamp [UCT]: 2024-12-26 08:43:29 Age [y:d:h:m:s]: 00:097:00:11:05
Block: 1183474 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 69105 RingCT/type: yes/0
Extra: 0179f487cd8ba09619f382c1c55390a5a39babb0ae0d82e65c4fbc0fb642313aae021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8bb03b457358653ea1821f3cd9df805d459981a7dcdd84d9841957585419da7f 0.600000000000 1669919 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": 1183484, "vin": [ { "gen": { "height": 1183474 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8bb03b457358653ea1821f3cd9df805d459981a7dcdd84d9841957585419da7f" } } ], "extra": [ 1, 121, 244, 135, 205, 139, 160, 150, 25, 243, 130, 193, 197, 83, 144, 165, 163, 155, 171, 176, 174, 13, 130, 230, 92, 79, 188, 15, 182, 66, 49, 58, 174, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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